clarification on entropy source accesss in vs/vu modes #141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| VS and VU always raises an exception; a read-only instruction causes an | ||
| illegal instruction exception, while a read-write instruction (that can | ||
| potentially be emulated) causes a virtual instruction exception only if | ||
| `mseccfg.seed=1`. Note that `mseccfg.useed` has no effect on the exception |
There was a problem hiding this comment.
mseccfg.seed=1 should be mseccfg.sseed=1, no?
There was a problem hiding this comment.
Yes, of course. Fixed now I think.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Further changes the behavior of VS/VU modes so that a virtual instruction exception is raised only for read-write accesses when mseccfg.sseed=1. Thanks to John Hauser for the clarification. Hopefully closes #139